@Christian-Ehrlicher Thanks dear. I will use this

@Imran-Hassan said in QT image display is not working without declaring openCV namedWindow in windows 10:

The problem is solved

great, so please don't forget to mark your post as such!

@hskoglund It worked!
I read the docs in OpenSSL provided with Qt (file INSTALL, src folder, section "Notes on shared libraries), where it states that:

On Windows build with MSVC or using MingW, shared libraries are named libcrypto-1_1.dll and libssl-1_1.dll for 32-bit Windows, libcrypto-1_1-x64.dll and libssl-1_1-x64.dll for 64-bit x86_64 Windows, and libcrypto-1_1-ia64.dll and libssl-1_1-ia64.dll for IA64 Windows. With MSVC, the import libraries are named libcrypto.lib and libssl.lib, while with MingW, they are named libcrypto.dll.a and libssl.dll.a.

Of course, files provided with Qt are build with MSVC which is just odd considering that I installed mingw only. Anyway, instead of going with installation of provided msvc packages (they are in the Qt folder tree, ms redist 2010) I downloaded OpenSLL 1.1.1d (or 1.1.1.4 as the dll description states) precompiled with mingw from official mirror.
Works like a charm.

What mislead me was that Qt started to provide OpenSSL binaries as toolkit whereas previously I always downloaded myself. Dumb me thought that toolkit would be oriented towards the build chain / compatible.

Anyway, thank you @hskoglund for the hint.

@daljit97 said in LGPL distribution in the Microsoft Store:

@sierdzio I suppose that could be an option I could consider, although I worry about piracy concerns.

Well, either worry about that or about Qt license costs. If you break the LGPL then you become the pirate ;-)

In this setup, if somebody gets the exe from you, they have already paid you. It does not solve the piracy problem, but does limit it somewhat.

I try with only one and after I added the 3 others to test. But indeed I get back to only one (Tools\mingw\bin) which contains g++.exe yes.

The above move is superflous so don't do it. Simply hide and show without repositioning the window. window managers and decoractions make the kind of move you are trying ambiguous.

If you must explicitly position the window then do move() before the initial show and always use that location, understanding that it won't be accurate (because the window manager decorations are not part of the wiget's geometry.

This is the price you pay for a plethora of plug-in widow managers with different capabilities and styles.

Hi
In most cases, there is nothing to change as Qt force is exactly to hide the platform details from you.
You will have to use Qt functions for paths and special folders
https://doc.qt.io/qt-5/qstandardpaths.html
and be a bit careful if you construct filenames etc but else
normally it will just work.

Bluetooth might be another story as the support pr platform differs
https://doc.qt.io/qt-5/qtbluetooth-index.html

Also, Windows 10 had something some oddities wanting you to manually pair devices but on Linux you could auto pair/discover.
I'm not sure the current status and it might just work.

Nice day to you too :)

@koahnig ok, another thing to try is to use clean settings, i.e. starting with -settingspath /tmp . I've experienced problems when using settings over several Creator versions, that were not reproduceable with clean settings.

You might also want to use a 4.11 snapshot instead 4.11.0.

Regards

Hi koahning,

I've had a similar problem. Maybe my bugreport helps:

https://bugreports.qt.io/browse/QTIFW-1003

After installing notepad++ and assigning ".vbs" extension to it, windows wasn't able to execute ".vbs" scripts anymore. Resetting the assignment in the regedit (HKEY_CLASSES_ROOT.vbs to "VBSFile") solves this issue.

Maybe this solves your issue, too.

Regards
Jazzco

@yijia

Maybe with different QLabel and QPixmap or QPicture

https://doc.qt.io/qt-5/qlabel.html#pixmap-prop
https://doc.qt.io/qt-5/qlabel.html#setPicture

Adding "[...]/mingw73_32/bin" to PATH worked! Thank you

Thanks @JonB . The problem seems gone when I remove these "process terminate" code.

yup looks like it is that bug, thanks guys

@aha_1980 said in Project ERROR: Cannot run compiler 'clang++':

You usually get *.pro.user.16fe832 files if you copy the project to another machine and open it there without deleting the .pro.user first.

...yes. I suppose that's a missing piece of information. The machine I developed on couldn't properly report to github, so I copied it to a flash drive.

Thanks for your help with this. The Qt Creator editor is a good alternative. I did run Dependency Walker - long time since I have looked at the output from this and not sure what I am seeing right now, but I've pasted the an abreviated version of the output below (too long to paste the whole thing) if it tells you something. Thanks again.

| System Information |

| Search Order |

* Legend: F File E Error (path not valid) * *

Side-by-Side components (Windows 2000/XP/2003/Vista/+)
[F ] c:\windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.2938_none_c58b03c797c07d8c\COMCTL32.DLL
[F ] c:\windows\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.2969_none_f678e0c2f2505d00\GDIPLUS.DLL
The system's "KnownDLLs" list
[F ] c:\windows\system32\ADVAPI32.DLL
[F ] c:\windows\system32\BCRYPTPRIMITIVES.DLL
[F ] c:\windows\system32\CFGMGR32.DLL
[F ] c:\windows\system32\CLBCATQ.DLL
[F ] c:\windows\system32\COMBASE.DLL
[F ] c:\windows\system32\COMCTL32.DLL
[F ] c:\windows\system32\COMDLG32.DLL
[F ] c:\windows\system32\COML2.DLL
[F ] c:\windows\system32\CRYPT32.DLL
[F ] c:\windows\system32\DIFXAPI.DLL
[F ] c:\windows\system32\GDI32.DLL
[F ] c:\windows\system32\GDI32FULL.DLL
[F ] c:\windows\system32\GDIPLUS.DLL
[F ] c:\windows\system32\IMAGEHLP.DLL
[F ] c:\windows\system32\IMM32.DLL
[F ] c:\windows\system32\KERNEL.APPCORE.DLL
[F ] c:\windows\system32\KERNEL32.DLL
[F ] c:\windows\system32\KERNELBASE.DLL
[F ] c:\windows\system32\LPK.DLL
[F ] c:\windows\system32\MSASN1.DLL
[F ] c:\windows\system32\MSCTF.DLL
[F ] c:\windows\system32\MSVCP_WIN.DLL
[F ] c:\windows\system32\MSVCRT.DLL
[F ] c:\windows\system32\NORMALIZ.DLL
[F ] c:\windows\system32\NSI.DLL
[F ] c:\windows\system32\NTDLL.DLL
[F ] c:\windows\system32\NTDLL.DLL
[F ] c:\windows\system32\OLE32.DLL
[F ] c:\windows\system32\OLEAUT32.DLL
[F ] c:\windows\system32\POWRPROF.DLL
[F ] c:\windows\system32\PROFAPI.DLL
[F ] c:\windows\system32\PSAPI.DLL
[F ] c:\windows\system32\RPCRT4.DLL
[F ] c:\windows\system32\SECHOST.DLL
[F ] c:\windows\system32\SETUPAPI.DLL
[F ] c:\windows\system32\SHCORE.DLL
[F ] c:\windows\system32\SHELL32.DLL
[F ] c:\windows\system32\SHLWAPI.DLL
[F ] c:\windows\system32\UCRTBASE.DLL
[F ] c:\windows\system32\USER32.DLL
[F ] c:\windows\system32\WIN32U.DLL
[F ] c:\windows\system32\WINDOWS.STORAGE.DLL
[F ] c:\windows\system32\WINTRUST.DLL
[F ] c:\windows\system32\WLDAP32.DLL
[F ] c:\windows\system32\WOW64.DLL
[F ] c:\windows\system32\WOW64CPU.DLL
[F ] c:\windows\system32\WOW64WIN.DLL
[F ] c:\windows\system32\WS2_32.DLL
The application directory
[ ] C:\Qt\5.12.3\msvc2015_64\bin
The 32-bit system directory
[ ] C:\Windows\system32
The 16-bit system directory (Windows NT/2000/XP/2003/Vista/+)
[ ] C:\Windows\system
The system's root OS directory
[ ] C:\Windows
The application's registered "App Paths" directories
The system's "PATH" environment variable directories
[ ] C:\Program Files\Microsoft MPI\Bin
[ ] C:\Windows\system32
[ ] C:\Windows
[ ] c:\Qt\5.12.3\bin\

| Module Dependency Tree |

* Legend: F Forwarded Module ? Missing Module 6 64-bit Module * D Delay Load Module ! Invalid Module * * Dynamic Module E Import/Export Mismatch or Load Failure * ^ Duplicate Module * *

[ 6] DESIGNER.EXE
[ 6] QT5DESIGNERCOMPONENTS.DLL
[ ^6] QT5DESIGNER.DLL
[ ^6] QT5WIDGETS.DLL
[ ^6] QT5GUI.DLL
[ ^6] QT5XML.DLL
[ ^6] QT5CORE.DLL
[ E ] KERNEL32.DLL
[FE ] NTDLL.DLL
[ E ] VCRUNTIME140.DLL
[ ^6] API-MS-WIN-CRT-RUNTIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STRING-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-HEAP-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ 6] QT5DESIGNER.DLL
[ ^6] QT5WIDGETS.DLL
[ ^6] QT5GUI.DLL
[ ^6] QT5XML.DLL
[ ^6] QT5CORE.DLL
[ E ] MSVCP140.DLL
[ E ] VCRUNTIME140.DLL
[ ^6] API-MS-WIN-CRT-HEAP-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-LOCALE-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STRING-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-RUNTIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STDIO-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ E6] API-MS-WIN-CRT-MATH-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-CONVERT-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-FILESYSTEM-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-TIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-ENVIRONMENT-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-UTILITY-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ E ] KERNEL32.DLL
[FE ] NTDLL.DLL
[DE ] CONCRT140.DLL
[ E ] MSVCP140.DLL
[ E ] VCRUNTIME140.DLL
[ ^6] API-MS-WIN-CRT-RUNTIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-HEAP-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ E6] API-MS-WIN-CRT-MATH-L1-1-0.DLL
[ ^6] API-MS-WIN-CRT-STRING-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STDIO-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ E ] KERNEL32.DLL
[FE ] NTDLL.DLL
[ E ] KERNEL32.DLL
[FE ] NTDLL.DLL
[ E ] VCRUNTIME140.DLL
[ ^6] API-MS-WIN-CRT-MATH-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-RUNTIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STRING-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STDIO-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-HEAP-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ 6] QT5PRINTSUPPORT.DLL
[ ^6] QT5WIDGETS.DLL
[ ^6] QT5GUI.DLL
[ ^6] QT5CORE.DLL
[ E ] WINSPOOL.DRV
[ E ] COMDLG32.DLL
[ E ] GDI32.DLL
[ E ] USER32.DLL
[ E ] KERNEL32.DLL
[FE ] NTDLL.DLL
[ E ] VCRUNTIME140.DLL
[ ^6] API-MS-WIN-CRT-STDIO-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-HEAP-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-MATH-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-RUNTIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ 6] QT5WIDGETS.DLL
[ ^6] QT5GUI.DLL
[ ^6] QT5CORE.DLL
[ E ] UXTHEME.DLL
[ E ] MSVCRT.DLL
[ ? ] API-MS-WIN-CORE-LIBRARYLOADER-L1-2-0.DLL
[ E6] API-MS-WIN-CORE-SYNCH-L1-2-0.DLL
[FE ] KERNEL32.DLL
[FE6] API-MS-WIN-CORE-SYNCH-L1-1-0.DLL
[ ? ] API-MS-WIN-CORE-HEAP-L1-2-0.DLL
[ ? ] API-MS-WIN-CORE-ERRORHANDLING-L1-1-1.DLL
[ ? ] API-MS-WIN-CORE-PROCESSTHREADS-L1-1-2.DLL
[ ? ] API-MS-WIN-CORE-LOCALIZATION-L1-2-1.DLL
[ ? ] API-MS-WIN-CORE-DEBUG-L1-1-1.DLL
[ ^6] API-MS-WIN-CORE-HANDLE-L1-1-0.DLL
[FE ] KERNEL32.DLL
[ ? ] API-MS-WIN-CORE-SYSINFO-L1-2-1.DLL
[ ? ] API-MS-WIN-CORE-LIBRARYLOADER-L1-2-2.DLL
[ ? ] API-MS-WIN-CORE-FILE-L1-2-1.DLL
[ ^6] API-MS-WIN-CORE-STRING-L1-1-0.DLL
[FE ] KERNEL32.DLL
[ ^6] API-MS-WIN-CORE-UTIL-L1-1-0.DLL
[FE ] KERNEL32.DLL
[FE ] NTDLL.DLL
[ ? ] API-MS-WIN-CORE-WINRT-ERROR-L1-1-1.DLL
[ ? ] API-MS-WIN-CORE-REGISTRY-L1-1-0.DLL
[ ? ] API-MS-WIN-SECURITY-BASE-L1-2-0.DLL
[ ? ] API-MS-WIN-CORE-HEAP-L2-1-0.DLL
[ ? ] API-MS-WIN-CORE-MEMORY-L1-1-2.DLL
[ ^6] API-MS-WIN-CORE-PROFILE-L1-1-0.DLL
[FE ] KERNEL32.DLL
[ ? ] API-MS-WIN-CORE-STRING-L2-1-0.DLL
[ ? ] API-MS-WIN-CORE-PROCESSENVIRONMENT-L1-2-0.DLL
[ ^6] API-MS-WIN-CORE-TIMEZONE-L1-1-0.DLL
[FE ] KERNEL32.DLL
[ ? ] API-MS-WIN-CORE-SIDEBYSIDE-L1-1-0.DLL
[ ? ] API-MS-WIN-CORE-ATOMS-L1-1-0.DLL
[ ? ] API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-1.DLL
[ ? ] API-MS-WIN-CORE-STRING-OBSOLETE-L1-1-0.DLL
[ ? ] API-MS-WIN-CORE-SHLWAPI-OBSOLETE-L1-2-0.DLL
[ ? ] API-MS-WIN-CORE-LOCALIZATION-OBSOLETE-L1-3-0.DLL
[ E ] NTDLL.DLL
[ E ] GDI32.DLL
[ E ] USER32.DLL
[FE ] NTDLL.DLL
[ ? ] API-MS-WIN-CORE-DELAYLOAD-L1-1-1.DLL
[D? ] API-MS-WIN-CORE-COM-L1-1-1.DLL
[DE ] OLEAUT32.DLL
[D? ] API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
[D? ] API-MS-WIN-SECURITY-SDDL-L1-1-0.DLL
[DE ] CRYPTSP.DLL
[DE ] DWMAPI.DLL
[DE ] WINDOWSCODECS.DLL

...

| Module List |*

* Legend: D Delay Load Module ? Missing Module 6 64-bit Module * * Dynamic Module ! Invalid Module * E Import/Export Mismatch or Load Failure * * Module File Time Stamp Link Time Stamp File Size Attr. Link Checksum Real Checksum CPU Subsystem Symbols Preferred Base Actual Base Virtual Size Load Order File Ver Product Ver Image Ver Linker Ver OS Ver Subsystem Ver

[ ? ] API-MS-WIN-CORE-APIQUERY-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-APPCOMPAT-L1-1-1.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-APPINIT-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-ATOMS-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-CALENDAR-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-COM-L1-1-0 Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-COM-L1-1-1.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-COM-MIDLPROXYSTUB-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).

| Log |*

Error: At least one required implicit or forwarded dependency was not found.
Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Error: A circular dependency was detected.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

@oblivioncth said in Building 5.12.1 32-bit static Qt for MSVC on Windows 10: The system cannot find the file specified (qgltf5.pdb).:

C:\Engineering\Development\Qt\Tools\QtCreator\bin\jom -j 8

I wanted to keep the versions for the standard and static versions consistent, but its not like it would really matter since its just a small revision difference. So, I attempted to build 5.12.3 this time and while I was at it I grabbed the dynamically linked version of 5.12.3 from the maintenance tool as well.

This time I ran the Visual Studio Native Tools command prompt as an administrator since I figured that had a shot at mattering even though I didn't see it mentioned anywhere and wasn't doing this is a UAC protected directory.

And... it built completely with no issues and I was able to produced a statically linked version of the app I'm working on like I wanted to. I don't know if there was a bug in the 5.12.3 source, if it actually was running the prompt as administrator, if there was just a simultaneous access issue with some of the files/tools on the last run, or if it was just a fluke, but everything works fine now.

The build ended on the same two lines but succeeded in copying qgltf.pdb instead of not finding it and the process took much longer than the previous attempt, so I'm guessing that there were errors earlier in the process that didn't stop the build script so I didn't catch them.